read committed造句

• Read committed database engine default level
  已提交读（数据库引擎的默认级别）
• Read committed using row versioning
  使用行版本控制的read committed
• Read committed read uncommitted
  读取提交的结果
• Both implementations meet the ansi definition of read committed isolation
  两个实现都满足已提交读隔离的ansi定义。
• Off transactions specifying the read committed isolation level use locking
  指定read _ committed隔离级别的事务使用锁定。
• This leaves you a choice between read committed and repeatable read
  剩下的也就是在“授权读取”和“可重复读取”之间选择了。
• Transactions specifying the read committed isolation level use row versioning instead of locking
  指定read _ committed隔离级别的事务使用行版本控制而不是锁定。
• When off is specified , transactions that specify the read committed isolation level use locking
  当指定为off时，指定read _ committed隔离级别的事务将使用锁定。
• Specifies that read operations comply with the rules for the read committed isolation level by using locking
  指定读操作使用锁定来遵循有关read committed隔离级别的规则。
• One is a new implementation of read committed isolation , and one is a new transaction isolation level , snapshot
  一个是已提交读隔离的新实现，另一个是新事务隔离级别（快照） 。
• Readpast can only be specified in transactions operating at the read committed or repeatable read isolation levels
  仅可在运行于read committed或repeatable read隔离级别的事务中指定readpast 。
• When on is specified , transactions specifying the read committed isolation level use row versioning instead of locking
  当指定为on时，指定read _ committed隔离级别的事务将使用行版本控制而不是锁定。
• Read committed isolation using row versioning is enabled by setting the read committed snapshot database option on
  将read _ committed _ snapshot数据库选项设置为on可启用使用行版本控制的已提交读隔离。
• Specifies that read operations comply with the rules for the read committed isolation level by using either locking or row versioning
  指定读操作使用锁定或行版本控制来遵循有关read committed隔离级别的规则。
• If the database option read committed snapshot is on , the database engine does not acquire locks and uses row versioning
  如果数据库选项read _ committed _ snapshot为on ，则数据库引擎不获取锁，并使用行版本控制。
• When a transaction runs at the read committed isolation level , all statements see a snapshot of data as it exists at the start of the statement
  当事务在read _ committed隔离级别运行时，所有的语句都将数据快照视为位于语句的开头。
• When a transaction runs at the read committed isolation level , all statements see a snapshot of data as it exists at the start of the statement
  当事务在read _ committed隔离级别运行时，所有的语句都将数据快照视为位于语句的开头。
• Row versions that are generated by data modification transactions in a database that uses snapshot or read committed using row versioning isolation levels
  由使用已提交读快照隔离或快照隔离级别的数据库中的数据修改事务生成的行版本。
• When the read committed snapshot database option is on , read committed transactions provide statement - level read consistency using row versioning
  Read _ committed _ snapshot数据库选项为on时， read _ committed事务通过使用行版本控制提供语句级读取一致性。
• When the read committed snapshot database option is set on , read committed isolation uses row versioning to provide statement - level read consistency
  将read _ commited _ snapshot数据库选项设置为on时，已提交读隔离使用行版本控制提供语句级别的读取一致性。